\chapter*{Abstract}

Providing accessible products has recently left  to be a differential
feature of certain companies. Accessibility, today, is a fundamental requirement
of any developed solution, indicating primarily respect and care to
customers.
This statement is especially true for products designed to the Internet which is
the gateway of all  world intercommunication. The Internet has showed to be the
fastest and cheapest technology to acquire information, and has forced legacy
technologies (banking services, for example) to adapt itself so that people with
permanent or momentary difficulties can be able to interact with society.
However, to give an accessible product is not always an easy task. In addition to several different classes of disabilities / difficulties (which leads to
different accessibility problems), lack of training and experience in the area
makes developers producing code in a wrong way, resulting in an inaccessible
product.
The process models and software development frameworks have not been adapted in a
consistent and homogeneous way, contemplating the accessibility in the software
factory. We are going through a transition phase between from the HTML and
XHTML 4 to HTML 5, which among other things, aims to deliver a semantic web and
to treat specific problems of accessibility, but it's not yet fully
consolidated.
Finally, the tools available to developers cannot effectively assist developers to
deliver an affordable product. In this work it is considered that the accessibility requirements should be taken into account during all phases of software development, ie, must evolve from initial requirements analysis to the phase of software testing in order to obtain accessibility as an attribute of software quality of the final product. Thus, we sought primarily to create an approach that could promote accessibility requirements traceability from conception to the coding phase. This approach has associated Requirements, UML models and implementation techniques for accessibility, mapped in an accessibility ontology. In addition, we developed a plugin for Eclipse that promoted the association of technical implementation of accessibility and traceability matrix. We created a proof of concept with the proposal to assess whether the objectives were achieved. The work showed that it is possible to check, automatically, the traceability of accessibility requirements as well as its implementation techniques, from Requirements Engineering phase to Coding phase.

\textbf{Keywords:} \textit{accessibility, requirement traceability,
software development process, CASE tool.}

\label{abstract}